feat(server-utils): Implement orchestrion-based instrumentation for vercel-ai v6#21658
feat(server-utils): Implement orchestrion-based instrumentation for vercel-ai v6#21658mydea wants to merge 4 commits into
Conversation
9145703 to
abad3a9
Compare
3417464 to
d05d40e
Compare
size-limit report 📦
|
d05d40e to
98fac43
Compare
JPeer264
left a comment
There was a problem hiding this comment.
Haven't found any major issues. Tests are failing though and clanker has some objections
| return isRecord(model) ? asString(model[field]) : undefined; | ||
| } | ||
|
|
||
| function asString(value: unknown): string | undefined { |
There was a problem hiding this comment.
super-l: Maybe it makes sense to outsource these functions in a helper? vercel-ai-dc-subscriber.ts is also using some of the helpers
05fd48d to
89bf321
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 89bf321. Configure here.
89bf321 to
c3f5431
Compare

When using orchestrion, this replaces the regular
vercelAiIntegrationwith the channel-variant. This today supports vercel ai v6 and v7 (v5/v4 support TBD).Test coverage exists and everything passes. This does not add any event processors etc. anymore, everything works inside of the integrations.
OTEL Spans emitted directly by vercel-ai v6 or below are ignored to avoid double instrumentation.